Systems and methods for machine to machine device control and triggering

ABSTRACT

Systems and methods for control and triggering of machine to machine (M2M) devices (e.g., smart meters). More specifically how to allow an M2M service provider (e.g., utility company) to use an operator&#39;s network to communicate with the M2M device connected with a UE/GW associated with the operator&#39;s network. The M2M service provider may receive identification of the UE/GW, but not for the M2M device. By transmitting an identifier for the M2M device along with an identifier for the UE/GW, the network operator may define establish and maintain a communication path specific to M2M devices. Similar techniques may be incorporated to allow the M2M service provider to locate and trigger the M2M device.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a Division of U.S. Non-Provisional application Ser.No. 13/691,347, entitled “SYSTEMS AND METHODS FOR MACHINE TO MACHINEDEVICE CONTROL AND TRIGGERING,” filed on Nov. 30, 2012, which claims thebenefit of U.S. Provisional Application Ser. No. 61/567,537, entitled“SYSTEMS AND METHODS FOR MACHINE TO MACHINE DEVICE CONTROL ANDTRIGGERING” and filed on Dec. 6, 2011, and U.S. Provisional ApplicationSer. No. 61/596,150, entitled “SYSTEMS AND METHODS FOR MACHINE TOMACHINE DEVICE CONTROL AND TRIGGERING” and filed on Feb. 7, 2012, whichare expressly incorporated by reference herein in their entirety.

BACKGROUND

Field

The present application relates generally to communication systems andmore specifically to control and triggering methods and devices formachine to machine communications.

Background

In many communication systems, communications networks are used toexchange messages among several interacting spatially-separated devices.Networks may be classified according to geographic scope, which couldbe, for example, a metropolitan area, a local area, or a personal area.Such networks would be designated respectively as a wide area network(WAN), metropolitan area network (MAN), local area network (LAN), orpersonal area network (PAN). Networks also differ according to theswitching/routing technique used to interconnect the various networknodes and devices (e.g., circuit switching versus packet switching), thetype of physical media employed for transmission (e.g., wired versuswireless), and the set of communication protocols used (e.g., Internetprotocol suite, SONET (Synchronous Optical Networking), Ethernet, etc.).

Wireless networks are often preferred when the network elements aremobile and thus have dynamic connectivity needs, or if the networkarchitecture is formed in an ad hoc, rather than fixed, topology.Wireless networks employ intangible physical media in an unguidedpropagation mode using electromagnetic waves in the radio, microwave,infra-red, optical, etc. frequency bands. Wireless networksadvantageously facilitate user mobility and rapid field deployment whencompared to fixed wired networks.

As networks proliferate, the types of network elements connected theretoalso expand. One type of network elements being introduced are machineto machine (M2M) elements. Examples of M2M elements include a smartutility meter (“smartmeter”), seismographs, vehicles, and appliances. AnM2M element may connect to a network through a user equipment (e.g.,smartphone, WiFi router). Accordingly, improvements to communicationsystems may be desirable to improve communication via the network, suchas communication from an M2M service provider (e.g., utility company),with a connected M2M element.

SUMMARY

The methods and devices described each have several aspects, no singleone of which is solely responsible for its desirable attributes. Withoutlimiting the scope of this disclosure as expressed by the claims whichfollow, some features will now be discussed briefly. After consideringthis discussion, and particularly after reading the section entitled“Detailed Description” one will understand how the features describedprovide advantages that include identification of and communication withM2M devices attached to a user equipment.

In one innovative aspect, a method of binding a plurality of devices toa user equipment is provided. The method includes receiving, via a firstnetwork, a message from at least one of the plurality of devices, themessage including information identifying a device of the plurality ofdevices connected with the user equipment. The method includes assigninga device connection identifier to the device, the device connectionidentifier including at least a portion of a user equipment identifierassociated with the user equipment. The method includes transmitting,via a second network, information indicative of the assignment of thedevice connection identifier to a network operator, such that datacommunication to the device from the network operator is based at leastin part on the device connection identifier.

In another innovative aspect, an apparatus for locally hosting aplurality of communication devices is provided. The apparatus includes areceiver configured to receive, via a first network, a message from atleast one of the plurality of communication devices, the messageincluding information identifying the communication device connectedwith the apparatus. The apparatus includes an assignment circuitconfigured to assign a device connection identifier to the communicationdevice, the device connection identifier including at least a portion ofa user equipment identifier associated with the apparatus. The apparatusincludes a transmitter configured to transmit, via a second network,information indicative of the assignment of the device connectionidentifier to a network operator, such that data communication to thecommunication device from the network operator is based at least in parton the device connection identifier.

In another innovative aspect, an apparatus for locally hosting aplurality of communication devices is provided. The apparatus includesmeans for receiving, via a first network, a message from at least one ofthe plurality of communication devices, the message includinginformation identifying the communication device connected with theapparatus. The apparatus includes means for assigning a deviceconnection identifier to the communication device, the device connectionidentifier including at least a portion of a user equipment identifierassociated with the apparatus. The apparatus includes means fortransmitting, via a second network, information indicative of theassignment of the device connection identifier to a network operator,such that data communication to the communication device from thenetwork operator is based at least in part on the device connectionidentifier.

In another innovative aspect, a computer-readable storage mediumcomprising instructions executable by a processor of an apparatus forlocally hosting a plurality of communication devices is provided. Theinstructions cause the apparatus to receive a message from at least oneof the plurality of communication devices, the message includinginformation identifying the communication device connected with theapparatus. The instructions cause the apparatus to assign a deviceconnection identifier to the communication device, the device connectionidentifier including at least a portion of a user equipment identifierassociated with the apparatus. The instructions cause the apparatus totransmit, via a second network, information indicative of the assignmentof the device connection identifier to a network operator, such thatdata communication to the communication device from the network operatoris based at least in part on the device connection identifier.

In a further innovative aspect, a method of binding a plurality ofdevices to a user equipment is provided. The method includestransmitting, via a first network from the user equipment to a networkoperator, registration information including an identifier for at leastone of the plurality of devices connected with the user equipment via asecond network. The method includes receiving a device connectionidentifier for the device from the network operator via the firstnetwork, the device connection identifier including at least a portionof a user equipment identifier associated with the user equipment, thedevice connection identifier indicating a connection between the deviceand the user equipment on the second network. The method includesreceiving a data communication from the network operator based at leastin part on the device connection identifier.

In yet another innovative aspect, an apparatus for locally hosting aplurality of wireless devices is provided. The apparatus includes atransmitter configured to transmit from the apparatus to a networkoperator via a first network registration information including anidentifier for at least one of the plurality of wireless devices. Thewireless device is connected with the apparatus via a second network.The apparatus includes a receiver configured to receive a deviceconnection identifier for the device from the network operator, thedevice connection identifier including at least a portion of a userequipment identifier associated with the apparatus. The deviceconnection identifier indicates a connection between the communicationdevice and the apparatus via the second network. The receiver is furtherconfigured to receive a data communication from the network operatorbased at least in part on the device connection identifier.

In a further innovative aspect, an apparatus for locally hosting aplurality of wireless devices is provided. The apparatus includes meansfor transmitting from the apparatus to a network operator via a firstnetwork registration information including an identifier for at leastone of the plurality of wireless devices connected with the apparatusvia a second network. The apparatus further includes means for receivinga device connection identifier for the device from the network operator,the device connection identifier including at least a portion of a userequipment identifier associated with the apparatus. The deviceconnection identifier indicates a connection between the wireless deviceand the apparatus on the second network. The apparatus also includesmeans for receiving, via the first network, a data communication fromthe network operator based at least in part on the device connectionidentifier.

In another innovative aspect, a computer-readable storage mediumcomprising instructions executable by a processor of an apparatus forlocally hosting a plurality of communication devices is provided. Theinstructions cause the apparatus to transmit from the apparatus to anetwork operator via a first network registration information includingan identifier for at least one of the plurality of communicationdevices, the communication device connected with the apparatus via asecond network. The instructions cause the apparatus to receive a deviceconnection identifier for the communication device from the networkoperator, the device connection identifier including at least a portionof a user equipment identifier associated with the apparatus. The deviceconnection identifier indicates a connection between the communicationdevice and the apparatus via the second network. The instructions causethe apparatus to receive, via the first network, a data communicationfrom the network operator based at least in part on the deviceconnection identifier.

In yet another innovative aspect, a method of binding a device to a userequipment is provided. The method includes transmitting, via a firstnetwork, a message from the device to the user equipment, the messageincluding information identifying the device connected with the userequipment via the first network. The method includes receiving, via thefirst network, a device connection identifier from the user equipment atthe device, the device connection identifier including at least aportion of a user equipment identifier associated with the userequipment. The method includes receiving a data communication from theuser equipment via the first network based at least in part on thedevice connection identifier, the data communication received by theuser equipment via a second network.

In a further innovative aspect, an apparatus for binding a userequipment is provided. The apparatus includes a transmitter configuredto transmit a message to the user equipment via a first network, themessage including information identifying the apparatus connected withthe user equipment. The apparatus includes a receiver configured toreceive a device connection identifier from the user equipment, thedevice connection identifier including at least a portion of a userequipment identifier associated with the user equipment. The receiver isfurther configured to receive a data communication from the userequipment based at least in part on the device connection identifier.The data communication is received by the user equipment via a secondnetwork.

In one innovative aspect, another apparatus for binding to a userequipment is provided. The apparatus includes means for transmitting amessage from the device to the user equipment via a first network, themessage including information identifying the apparatus connected withthe user equipment. The apparatus includes means for receiving a deviceconnection identifier from the user equipment at the apparatus via thefirst network. The device connection identifier includes at least aportion of a user equipment identifier associated with the userequipment. The apparatus includes means for receiving a datacommunication from the user equipment via the first network based atleast in part on the device connection identifier, the datacommunication received by the user equipment via a second network.

A computer-readable storage medium comprising instructions executable bya processor of an apparatus for binding to a user equipment is providedin a further innovative aspect. The instructions cause the apparatus totransmit a message from the device to the user equipment via a firstnetwork, the message including information identifying the apparatusconnected with the user equipment. The instructions cause the apparatusto receive a device connection identifier from the user equipment at theapparatus via the first network. The device connection identifierincludes at least a portion of a user equipment identifier associatedwith the user equipment. The instructions cause the apparatus to receivea data communication from the user equipment based at least in part onthe device connection identifier, the data communication received by theuser equipment via a second network.

In another innovative aspect, a method of triggering a device connectedto a user equipment is provided. The method includes receiving, at anoperator network, a device triggering request including an identifierassociated with the device to be triggered. The device is connected tothe user equipment via a first network. The method includes identifyingthe user equipment hosting the device based at least in part on theidentifier. The method includes initiating a communication link in asecond network to the user equipment, the communication link based atleast in part on information identifying the device to be triggered. Themethod includes transmitting, via the second network, the devicetriggering request to the user equipment.

An apparatus for triggering a device connected to a user equipment isprovided in another innovative aspect. The apparatus includes a receiverconfigured to receive, at an operator network, a device triggeringrequest including an identifier associated with the device to betriggered. The device is connected to the user equipment via a firstnetwork. The apparatus also includes a processor. The processor isconfigured to identify the user equipment hosting the device based atleast in part on the identifier. The processor is further configured toinitiate a communication link in a second network to the user equipment,the communication link based at least in part on information identifyingthe device to be triggered. The apparatus also includes a transmitterconfigured to transmit via the second network the device triggeringrequest to the user equipment.

Another apparatus for triggering a device connected to a user equipmentis provided in a further innovative aspect. The apparatus includes meansfor receiving, at an operator network, a device triggering requestincluding an identifier associated with the device to be triggered. Thedevice is connected to the user equipment via a first network. Theapparatus includes means for identifying the user equipment hosting thedevice based at least in part on the identifier. The apparatus includesmeans for initiating a communication link in a second network to theuser equipment, the communication link based at least in part oninformation identifying the device to be triggered. The apparatusincludes means for transmitting via the second network the devicetriggering request to the user equipment.

Another computer-readable storage medium comprising instructionsexecutable by a processor of an apparatus for triggering a deviceconnected to a user equipment is provided in a further innovativeaspect. The instructions cause the apparatus to receive at an operatornetwork a device triggering request including an identifier associatedwith the device to be triggered. The device is connected to the userequipment via a first network. The instructions cause the apparatus toidentify a the user equipment hosting the device based at least in parton the identifier. The instructions cause the apparatus to initiate acommunication link in a second network to the user equipment, thecommunication link based at least in part on information identifying thedevice to be triggered. The instructions cause the apparatus to transmitvia the second network the device triggering request to the userequipment.

In another innovative aspect, a method of communication to a devicehosted by a user equipment is provided. The method includes storing, atthe user equipment, information relating a network identifier for thedevice to a service identifier for the device. The method includesreceiving, at the user equipment from a network operator via a firstnetwork, routing information and the network identifier. The methodincludes receiving, at the user equipment from a network operator viathe first network, a message including the service identifier, themessage targeted for the device. The method includes obtaining therouting information and the network identifier based at least in part onthe service identifier. The method includes transmitting via a secondnetwork at least a portion of the message to the device, thetransmitting based at least in part on the obtained routing information.

An apparatus for communicating with a device locally hosted by theapparatus is provided in yet another innovative aspect. The apparatusincludes a memory storing information relating a network identifier forthe device to a service identifier for the device. The apparatusincludes a receiver configured to receive, from a network operator via afirst network, routing information and the network identifier. Thereceiver is further configured to receive a message via the firstnetwork including the service identifier, the message targeted for thedevice. The apparatus includes a processor configured to obtain therouting information and the network identifier based at least in part onthe service identifier. The apparatus includes a transmitter configuredto transmit via a second network at least a portion of the message tothe device, the transmitting based at least in part on the obtainedrouting information.

An apparatus for communicating with a device locally hosted by theapparatus is provided in a further innovative aspect. The apparatusincludes means for storing information relating a network identifier forthe device to a service identifier for the device. The apparatusincludes means for receiving, from a network operator via a firstnetwork, routing information and the network identifier. The apparatusincludes means for receiving, via the first network, a message includingthe service identifier, the message targeted for the device. Theapparatus includes means for obtaining the routing information and thenetwork identifier based at least in part on the service identifier. Theapparatus includes means for transmitting, via a second network, atleast a portion of the message to the device, the transmitting based atleast in part on the obtained routing information.

A computer-readable storage medium comprising instructions executable bya processor of an apparatus for communicating with a device locallyhosted by the apparatus. The instructions cause the apparatus to storeinformation relating a network identifier for the device to a serviceidentifier for the device. The instructions cause the apparatus toreceive, from a network operator via a first network, routinginformation and the network identifier. The instructions cause theapparatus to receive a message including the service identifier via thefirst network, the message targeted for the device. The instructionscause the apparatus to obtain the routing information and the networkidentifier based at least in part on the service identifier. Theinstructions cause the apparatus to transmit, via a second network, atleast a portion of the message to the device, the transmitting based atleast in part on the obtained routing information.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 shows an exemplary communication system.

FIG. 2 shows a functional block diagram of an exemplary device that maybe employed within the communication system of FIG. 1.

FIG. 3 shows an interaction diagram for various aspects of acommunication system.

FIG. 4 shows a call flow diagram for an exemplary device binding.

FIG. 5 shows a process flow diagram of an exemplary process for bindinga plurality of devices to a user equipment.

FIG. 6 shows a functional block diagram of another exemplary device thatmay be employed within the communication system of FIG. 1.

FIG. 7 shows a process flow diagram of another exemplary process forbinding a plurality of devices to a user equipment.

FIG. 8 shows a functional block diagram of another exemplary device thatmay be employed within the communication system of FIG. 1.

FIG. 9 shows a process flow diagram of an exemplary process of binding adevice to a user equipment.

FIG. 10 shows a functional block diagram of another exemplary devicethat may be employed within the communication system of FIG. 1.

FIG. 11 shows a process flow diagram of an exemplary process fortriggering a device hosted by a local host/user equipment.

FIG. 12 shows a functional block diagram of another exemplary devicethat may be employed within the communication system of FIG. 1.

FIG. 13 shows a process flow diagram of an exemplary process ofcommunication to a device through a local host/user equipment.

FIG. 14 shows a functional block diagram of another exemplary devicethat may be employed within the communication system of FIG. 1.

DETAILED DESCRIPTION

Various aspects of the novel apparatuses and methods are described morefully hereinafter with reference to the accompanying drawings. Theteachings disclosure may, however, be implemented in many differentforms and should not be construed as limited to any specific structureor function presented throughout this disclosure. Rather, these aspectsare provided so that this disclosure will be thorough and complete, andwill fully convey the scope of the disclosure to those skilled in theart. Based on the teachings herein one skilled in the art shouldappreciate that the scope of the disclosure is intended to cover anyaspect of the novel apparatuses and methods disclosed herein, whetherimplemented independently of or combined with any other aspect of thedisclosure. For example, an apparatus may be implemented or a method maybe practiced using any number of the aspects set forth herein. Inaddition, the scope of the description is intended to cover such anapparatus or method which is practiced using other structure,functionality, or structure and functionality in addition to or otherthan the various aspects set forth herein. Any aspect disclosed hereinmay be implemented by one or more elements of a claim.

Although particular aspects are described herein, many variations andpermutations of these aspects fall within the scope of the disclosure.Although some benefits and advantages of the preferred aspects arementioned, the scope of the disclosure is not intended to be limited toparticular benefits, uses, or objectives. Rather, aspects of thedisclosure are intended to be broadly applicable to differentcommunication technologies, system configurations, networks, andtransmission protocols, some of which are illustrated by way of examplein the figures and in the following description of the preferredaspects. The detailed description and drawings are merely illustrativeof the disclosure rather than limiting, the scope of the disclosurebeing defined by the appended claims and equivalents thereof.

Popular wireless network technologies may include various types ofwireless local area networks (WLANs). A WLAN may be used to interconnectnearby devices together, employing widely used networking protocols. Thevarious aspects described herein may apply to a communication standard,such as wireless protocols. For example, the various aspects describedherein may use Zigbee, WiFi, HomePlug, Bluetooth, Zwave, cellular, orother radio communications.

In some implementations, a communication network includes variousdevices which are the components that access the network. For example,there may be two types of devices: access points (“APs”) and clients(also referred to as stations, or “STAs”). In general, an AP serves as ahub or base station for the communication network and a STA serves as auser of the communication network. For example, a STA may be a laptopcomputer, a personal digital assistant (PDA), a mobile phone, etc. In anexample, a STA connects to an AP via a WiFi (e.g., IEEE 802.11 protocolsuch as 802.11ah) compliant wireless link to obtain general connectivityto the Internet or to other wide area networks.

An access point (“AP”) may also comprise, be implemented as, or known asa NodeB, Radio Network Controller (“RNC”), eNodeB, Base StationController (“BSC”), Base Transceiver Station (“BTS”), Base Station(“BS”), Transceiver Function (“TF”), Router, Transceiver, Hub, or someother terminology.

A station “STA” may also comprise, be implemented as, or be known as anaccess terminal (“AT”), a subscriber station, a subscriber unit, amobile station, a remote station, a remote terminal, a user terminal, auser agent, a user device, user equipment, or some other terminology. Insome implementations an access terminal may comprise a cellulartelephone, a telephone, a Session Initiation Protocol (“SIP”) phone, awireless local loop (“WLL”) station, a personal digital assistant(“PDA”), a handheld device, or some other suitable processing deviceconnected to a modem. Accordingly, one or more aspects taught herein maybe incorporated into a phone (e.g., a cellular phone or smartphone), acomputer (e.g., a laptop), a portable communication device, a headset, aportable computing device (e.g., a personal data assistant), anentertainment device (e.g., a music or video device, or a satelliteradio), a gaming device or system, a global positioning system device,an appliance, power generating/transmitting equipment, surveillanceequipment (e.g., seismograph, smoke detector, Geiger counter, camera),smartmeter, vending machine or any other suitable device that isconfigured to communicate via a wireless or wired medium in a machine tomachine fashion.

Some devices may be used for smart metering, in a smart grid network, orin smart appliances (e.g., appliances configurable in response totransmitted or detected signals). Such devices may provide sensorapplications or be used in home automation. The devices may instead orin addition be used in a healthcare context, for example for personalhealthcare. They may also be used for surveillance, to enableextended-range Internet connectivity (e.g. for use with hotspots), or toimplement machine-to-machine communications.

Prior to communicating with a network, a STA generally registers with anetwork. Registration may be done at power up, based on zones, based ontime (e.g., periodic), or parameter based. For example, in a cdma2000 1×system, a periodic registration system is used to ensure the STA may bereached. In some implementations, an AP transmits (e.g., broadcasts) aregistration period. If a STA has no traffic channel established, orother types of registration (e.g., signaling) during the registrationperiod, the STA is configured to transmit a registration at least onetime during the registration period to maintain presence on the network.This form of registration may also be included in EVDO, UMTS, LTE, HRPD,and PPP systems.

In some implementations, a first STA may provide a service to anotherSTA. For example, a website may be considered a service providing STAwherein the server hosting the website may be the service providing STA.A smartphone accessing the website may be considered the other STA. Thesmartphone and the website STAs may communicate through one or more APs.The AP connected with the smartphone identifies the smartphone and anycommunications associated therewith. The identification may beaccomplished through a registration protocol. Similar procedure may beused to connect server hosting the website. By this example, the networkof APs may be considered under the purview of a network operator. Thenetwork operator may control the devices identified to it for example byshaping the network traffic (e.g., latency, priority, bandwidth) orblocking certain traffic (e.g., packet level, source, destination, port,etc.).

As discussed above, networked technologies and network capable devicesare becoming more pervasive. In some instances, a device may access anetwork provided by a network provider through a user equipment such asa cable modem or mobile hot-spot. In this situation, the cable modem ormobile hot-spot may be configured to identify itself to the networkoperator to gain access to network services. However, once connected,various devices coupled with the cable modem or mobile hot-spot may usethe network services. In some implementations, the user equipment may bereferred to as a “gateway.”

One non-limiting advantage of the systems and methods described hereinis to allow a network operator the ability to identify and control thesedevices accessing an operator's network through devices such as a mobilehot-spot. By identifying not only the user equipment attached to thenetwork (e.g., mobile hot-spot), but also the devices attached to theuser equipment, traffic may be more finely controlled. For example, inthe machine to machine (M2M) context, it may be desirable to allow a M2Mcapable fire detector higher priority than, say, a M2M data collectiondevice (e.g., thermometer). The identification also allows the networkoperator to adjust subscription levels for various devices.

Another non-limiting advantage of the systems and methods described hereis to allow the network operator to locate the device connected to userequipment (UE). In the mobility context, the user equipment may operateon a cellular network. The user equipment may be mobile. In the casewhere a service provider wishes to send a signal (e.g., a trigger) to adevice attached to the user equipment, the network may be configured toidentify the location of the UE as well as the device.

A further non-limiting advantage of the systems and methods described isallowing multiple locally hosted devices to share a user equipmentconnection for data communication. The sharing may be implemented asparallel connection sharing whereby each hosted device may obtain aunique connection to the user equipment which can be used independent ofother device connections for forward or reverse link communication. Forexample, if the user equipment is configured for multiple-input andmultiple-output communications, the user equipment may receive and/ortransmit data for two or more hosted devices at or near the same pointin time. The reception and/or transmission need not be deferred whilewaiting for another device to complete communications.

FIG. 1 shows an exemplary communication system. The communication system100 may operate pursuant to a wireless standard. The communicationsystem 100 may include an AP 104, which communicates with STAs such as acomputer 106 c, a service provider server 106 b, a machine to machinedevice 106 a such as a vending machine, and a local access point (a.k.a.local host or gateway) 106 d (individually or collectively hereinafteridentified by 106). Each STA 106 may be configured to include anidentifier. For example, the local access point 106 d may include a userequipment identifier. The user equipment identifier may be used toidentify a local access point 106 d. In some implementations the userequipment identifier may uniquely identify the local access point 106 d.In some implementations, the user equipment identifier may be used inconjunction with other information (e.g., network operator) to uniquelyidentify the local access point 106 d. A user equipment identifier mayinclude an international mobility equipment identity or internationalmobility subscriber identity.

The local access point 106 d may be further configured to communicatewith one or more machine to machine devices 112 a, 112 b, and 112 c(collectively or individually hereinafter identified by 112) such as asmart utility meter or a smartmeter. In some implementations, a machineto machine device 112 may be associated with a machine to machineservice provider (e.g., utility company). Each machine to machine device112 may be configured to include a device identifier. The deviceidentifier may be used to identify a machine to machine device 112. Insome implementations the device identifier may uniquely identify themachine to machine device 112. In some implementations, the deviceidentifier may be used in conjunction with other information (e.g.,network operator, machine to machine service provider) to uniquelyidentify the machine to machine device 112. It will be appreciated thatwhile the local access point 106 d is described and shown as connectedto machine to machine devices 112, other wireless communication devicesmay be configured to communicate with the network via the local accesspoint 106 d. Examples of such wireless communications devices include anIP phone, a network enabled media player, and a network enabledappliance (e.g., washer, dryer, air conditioner, over, microwave, slowcooker).

A variety of processes and methods may be used for transmissions in thecommunication system 100 between the AP 104 and the STAs 106. Forexample, signals may be sent and received between the AP 104 and theSTAs 106 in accordance with OFDM/OFDMA techniques. If this is the case,the communication system 100 may be referred to as an OFDM/OFDMA system.Alternatively, signals may be sent and received between the AP 104 andthe STAs 106 in accordance with CDMA techniques. If this is the case,the communication system 100 may be referred to as a CDMA system. Insome implementations, the signals between the AP 104 and the STAs 106may be sent via a wired connections such as Ethernet, optical, cable,telephone, power line, and facsimile connections.

A communication link that facilitates transmission from the AP 104 toone or more of the STAs 106 may be referred to as a downlink (DL) 108,and a communication link that facilitates transmission from one or moreof the STAs 106 to the AP 104 may be referred to as an uplink (UL) 110.Alternatively, a downlink 108 may be referred to as a forward link or aforward channel, and an uplink 110 may be referred to as a reverse linkor a reverse channel.

The AP 104 may provide communication coverage in a basic service area(BSA) 102. The AP 104 along with the STAs 106 associated with the AP 104and that are configured to use the AP 104 for communication may bereferred to as a basic service set (BSS). The communication system 100may not have a central AP 104, but rather may function as a peer-to-peernetwork between the STAs 106. Accordingly, the functions of the AP 104described herein may alternatively be performed by a STA 106. Forexample, in some implementations, one or more STAs 106 may be locatedoutside the BSA 102.

In the system 100 shown in FIG. 1, unlike machine to machine device 106a, the machine to machine devices 112 a, 112 b, and 112 c may not becapable of initiating communication with the AP 104. Similarly, the AP104 may not be able to identify which devices are locally connected tothe local access point 106 d. For example, the AP 104 may receive acommunication from the service provider server 106 b, such as a demandresponse signal. This communication may be targeted to a specificsmartmeter 112 a. Accordingly, in some implementations it may bedesirable to register the specific smartmeter 112 a such that the AP 104may identify the specific smartmeter 112 a. This registration processwill be described in further detail below.

In another example, the machine to machine device 112 a may be anautomotive monitoring device included in an automobile. This type ofmachine to machine device 112 a may be configured to communicate via acellular device in the automobile. However, the machine to machinedevice 112 a may not be located in the same BSA 102 between datatransmissions. In this example, one way to communicate with the machineto machine device 112 a, is to first locate the cellular device.Accordingly, in some implementations it may be desirable to configurethe AP 104 to locate the specific machine to machine device 112 a in amobility setting. This may allow a service provider server 106 b totrigger the device 112 a. For example, an automotive manufacturer may bethe service provider. By this example, the service provider server 106 bmay be configured to retrieve diagnostic information from the automotivemonitoring device for further processing (e.g., generating maintenancereminders, troubleshooting, quality assurance, etc.).

The communication between the local access point 106 d and the machineto machine devices 112 may be a local communication protocol. Thecommunication may comprise a wired link between the machine to machinedevices 112 and the local access point 106 d (e.g., Ethernet, powerline, telephone cable, coaxial cable). The communication may comprise awireless link such as Peanut, Zigbee, WiFi, Bluetooth and the like.Multiple communication methods may be used to communicate with thevarious machine to machine devices 112. Furthermore, it will beappreciated that while in FIG. 1 all the machine to machine devices 112are shown as smartmeters, machine to machine devices of type may beconnected through the same local access point 106 d (e.g., smartmeter,smoke alarm, vending machine, etc.).

FIG. 2 shows a functional block diagram of an exemplary a device thatmay be employed within the communication system of FIG. 1. The device202 is an example of a device that may be configured to implement thevarious methods described herein. For example, the device 202 maycomprise the AP 104, one of the STAs 106, or a machine to machine device112.

The device 202 may include processor unit(s) 204 which control operationof the device 202. One or more of the processor unit(s) 204 may becollectively referred to as a central processing unit (CPU). Memory 206,which may include both read-only memory (ROM) and random access memory(RAM), provides instructions and data to the processor units 204. Aportion of the memory 206 may also include non-volatile random accessmemory (NVRAM). The processor unit(s) 204 may be configured to performlogical and arithmetic operations based on program instructions storedwithin the memory 206. The instructions in the memory 206 may beexecutable to implement the methods described herein.

When the device 202 is implemented or used as a transmitting node, theprocessor unit(s) 204 may be configured to select one of a plurality ofpacket formats, and to generate a packet having that format. Forexample, the processor unit(s) 204 may be configured to generate datapackets. When the device 202 is implemented or used as a receiving node,the processor unit(s) 204 may be configured to process received packets.The processor unit(s) 204 generate a packet for transmission to one ormore STAs 106 or machine to machine devices 112. A packet comprises aseries of data bits representing the data being exchanged between an AP104 and a STA 106/machine to machine device 112.

The processor unit(s) 204 may be implemented with any combination ofgeneral-purpose microprocessors, microcontrollers, digital signalprocessors (DSPs), field programmable gate array (FPGAs), programmablelogic devices (PLDs), controllers, state machines, gated logic, discretehardware components, dedicated hardware finite state machines, or anyother suitable entities that can perform calculations or othermanipulations of information. In an implementation where the processorunit(s) 204 comprise a DSP, the DSP may be configured to generate apacket for transmission. In some aspects, the packet may comprise aphysical layer data unit (PLDU).

The device 202 may also include machine-readable media for storingsoftware. The processor unit(s) 204 may comprise one or moremachine-readable media for storing software. Software shall be construedbroadly to mean any type of instructions, whether referred to assoftware, firmware, middleware, microcode, hardware descriptionlanguage, or otherwise. Instructions may include code (e.g., in sourcecode format, binary code format, executable code format, or any othersuitable format of code). The instructions, when executed by theprocessor unit(s) 204, cause the device 202 to perform the variousfunctions described herein.

The device 202 may include a transmitter 210 and/or a receiver 212 toallow transmission and reception, respectively, of data between thedevice 202 and a remote location. The transmitter 210 and receiver 212may be combined into a transceiver 214. An antenna 216 may beelectrically coupled with the transceiver 214. The device 202 may alsoinclude (not shown) multiple transmitters, multiple receivers, multipletransceivers, and/or multiple antennas.

The transmitter 210 may be configured to wirelessly transmit packetsand/or signals. For example, the transmitter 210 may be configured totransmit different types of packets generated by the processor unit(s)204, discussed above. The packets are made available to the transmitter210. For example, the processor unit(s) 204 may store a packet in thememory 206 and the transmitter 210 may be configured to retrieve thepacket. Once the transmitter 210 retrieves the packet, the transmitter210 transmits the packet to the device 202 via the antenna 216.

The antenna 216 on the device 202 may detect the transmittedpackets/signals. The receiver 212 may be configured to process thedetected packets/signals and make them available to the processorunit(s) 204. For example, the receiver 212 may store the packet inmemory 206 and the processor unit(s) 204 may be configured to retrievethe packet.

The device 202 may also include a signal detector 218 that may be usedin to detect and quantify the level of signals received by thetransceiver 214. The signal detector 218 may detect such signals astotal energy, energy per subcarrier per symbol, power spectral density,and other signals.

In some aspects, the device 202 may further comprise a user interface222. The user interface 222 may comprise a keypad, a microphone, aspeaker, and/or a display. The user interface 222 may include anyelement or component that conveys information to a user of the device202 and/or receives input from the user. The device 202 may also includea housing 208 surrounding one or more of the components included in thedevice 202.

The device 202 may also include an assignment circuit 228. For example,the assignment circuit 228 may be included in a device 202 implementedas a local access point 106. The assignment circuit 228 may beconfigured to assign a device connection identifier to each of thedevice identifiers, the device connection identifier including at leasta portion of a user equipment identifier associated with the localaccess point 106. For example, when the device 202 is configured tocommunicate via Ethernet with a machine to machine device 112, theassignment circuit 228 may receive a signal indicating a connection withthe machine to machine device 112. The device connection identifier maybe a composite identifier (e.g., a device identifier (e.g., IID, MAC-ID)and a connection identifier (e.g., port)). The assignment circuit 228may maintain a list of communication bindings with the AP 104 (e.g., inmemory 206). The assignment circuit 228 may then identify an unusedcommunication binding from the maintained list to be configured for themachine to machine device 112. The assignment circuit 228 may thenconfigure a communication pathway between the Ethernet connection andthe unused communication binding. This communication pathway may then beassociated with the machine to machine device 112 using the deviceidentifier. The device 202 may refer to the entire binding through theuse of a device connection identifier.

The assignment circuit 228 may provide the device connection identifierto the AP 104. For example, the assignment circuit 228 may store thedevice connection identifier in the memory 206. The transmitter 210 mayobtain the device connection identifier and transmit this to the AP 104.In some implementations, the transmitter 210 may be configured toidentify data packets transmitted from the machine to machine device 112an incorporate the device connection identifier on the packetstransmitted from the machine to machine device 116 through the device202. Accordingly, the AP 104 can identify that a particular packet notonly was transmitted by a particular STA, but also that a particularpacket was transmitted by a particular device connected to the STA.

The device 202 may also include a quality of service circuit 232. Aquality of service circuit 232 may be included in a STA 106, AP 104, ormachine to machine device 112. A local access point 106 d may include aquality of service circuit 232 configured to perform two levels ofquality of service, that is to maintain quality of service between eachconnected machine to machine device 112 as well as maintain quality ofservice with the AP 104.

The quality of service circuit 232 may be configured to maintain variousoperational attributes that affect the quality of the services providedor received. The transmitter 210 and/or receiver may be configured tocommunicate with the quality of service circuit 232 to control how datais transmitted or received. For example, quality of service circuit 232may be configured to identify a maximum bandwidth for a particularcommunication flow. The quality of service information may be stored inthe memory 206. The quality of service information may be received froma device providing the service such as a service provider server 106 b.In some implementation, the quality of service circuit 232 may beconfigured to derive the quality of service information for examplebased on a device class of the machine to machine device 112. Forinstance, a device that is in a low priority class such as datareporting device may be assigned lower quality of service during busyperiods. Conversely, a device that is in a high priority class such as asmoke detector may be assigned a higher quality of service to ensure analarm is raised in a timely fashion. In further implementations, thequality of service circuit 232 may be configured to negotiate quality ofservice with another device (e.g., machine to machine device 112negotiating with a local access point 106 d, STA 106 negotiating with anAP 104).

In some implementations, the quality of service may be specified using atuple. The quality of service tuple may include the device connectionidentifier. In some implementations, an RSVP tuple may be used tospecify the quality of service information.

The device 202 may also include a registration circuit 234. Theregistration circuit 234 may be configured to allow the device 202 toaccess services. For example, when the device 202 is configured as alocal access point 106 d, the local access point 106 d may provide itsuser equipment identifier to the AP 104 as part of establishing acommunication link therewith. In some implementations, the userequipment identifier may be used by the AP 104 to identify machine tomachine device bindings for the device. For example, when deploying asmartmeter system, it may be known, a priori, how many meters 112 willbe attached to a given local access point 106 d. Accordingly, in thisimplementation, the local access point 106 d may provide its identifierto the AP 104 and the AP 104 may determine the appropriate communicationbinding for the device. For example, the AP 104 may query a data storagemaintained by a service provider to determine the number of meterattached to the identified address. In other implementations, the AP 104may be configured to provide a pre-determined number of bindings perlocal access point 106 d. In this implementation, the AP 104 may consulta subscription registry of user equipment identifiers and provide thepre-determined number of bindings based on a subscription for localaccess point 106 d. Similar techniques may also be used to providequality of service information to the quality of service circuit 232. Anaccounting circuit (not shown) may also be included to generateaccounting information based on the device connection identifier, deviceclass, network usage (e.g., time, quantity, type), and the like. Theaccounting information may then be used to control subsequent accesssuch as according to a subscription and/or provide billing informationbased on the accounting information for the device.

The device may further include a locator circuit 236. For example whendeploying the device 202 as an AP 104, the locator circuit 236 may beconfigured to identify a location for a local host/user equipment. Thelocation may be identified based at least in part on one or more of theuser equipment identifier and a device identifier for a machine tomachine device 112 attached to the local host/user equipment. Forexample, in the mobility example discussed above, it may be desirable totrigger the machine to machine device 112. However, if the machine tomachine device 112 is mobile, the location of the STA 106 associatedwith the machine to machine device 112 may change. The locator circuit236 may store the location (e.g., home, mobile) of the STA 106. Usingthe user equipment identifier and/or the device identifier, the locatorcircuit 236 may be configured to identify the location of the STA 106(e.g., query).

The device may also include an encryption circuit 238. The encryptioncircuit 238 may be configured to protect information transmitted fromthe device 202. For example, the device identifier may be integritysigned by the device 202. This can prevent unauthorized machine tomachine devices from “spoofing” as legitimate machine to machine devices112. The encryption circuit 238 may include a key store to maintain apublic or private encryption key, a digital certificate, asynchronization value, a random number generator, or the like. Thetransmitter 210 may be configured to provide data to the encryptioncircuit 238 prior to transmission for encryption. Once the data has beenencrypted, the encryption circuit 238 may be configured to provideinformation about the encryption to the transmitter 210 to betransmitted to allow the receiving device to decrypt the information.The encryption circuit 238 may also be configured to decrypt informationby reversing the above for a received signal.

The device may also include a binding manager 240. The binding manager240 may be included in a device 202 when implemented as a local accesspoint 106 d or as an AP 104. The binding manager 240 may be configuredto receive binding information for the plurality of devices. In someimplementations, the binding manager 240 may be configured determinebinding information for each of the one or more machine to machinedevices 112 based at least in part on the user equipment identifier forthe local access point 106 d. For example, in an implementation wherethe AP 104 provides a pre-determined binding assignment to the localaccess point 106 d, the binding manager 240 may be configured to processthe binding assignments. In one implementation, the binding manager 240includes a memory or is configured to communicate with the memory 206.

The device may also include a circuit call manager 242. The circuit callmanager 242 may be included in a device implemented as an AP 104. Forexample, in an implementation where a service provider transmits amessage to the AP 104 for a machine to machine device 112, the circuitcall manager 242 may be configured to initiate a circuit call to thelocal host/user equipment. The circuit call manager 242 may includeincluding information identifying the device to be triggered to allowproper routing of the trigger to the machine to machine device 112. Insome implementations, the circuit call manager 242 may be configured tomanage cdma2000 1× circuit communications such as circuit calls andshort message delivery point-to-point (SMDPP) signaling.

The various components of the device 202 may be coupled together by abus system 226. The bus system 226 may include a data bus, for example,as well as a power bus, a control signal bus, and a status signal bus inaddition to the data bus. Those of skill in the art will appreciate thecomponents of the device 202 may be coupled together or accept orprovide inputs to each other using some other mechanism.

Although a number of separate components are illustrated in FIG. 2,those of skill in the art will recognize that one or more of thecomponents may be combined or commonly implemented. For example, theprocessor unit(s) 204 may be used to implement not only thefunctionality described above with respect to the processor unit(s) 204,but also to implement the functionality described above with respect tothe signal detector 218. Further, each of the components illustrated inFIG. 2 may be implemented using a plurality of separate elements.

FIG. 3 shows an interaction diagram for various aspects of acommunication system. The system 300 includes two user equipment (UE)devices 302 a and 302 b (collective or individually hereinafteridentified as 302). In some implementation, the user equipment devices302 may be implemented as local access points. The user equipment 302 aincludes a machine to machine client application (M2M APP) 304. Thismachine to machine client application 304 may be configured tocommunicate with a machine to machine server application 318. Forexample, the machine to machine client application 304 may be a datacollection application configured to transmit a meter reading to themachine to machine server application 318 for further processing (e.g.,safety monitoring, billing).

The user equipment 302 b shown in FIG. 3 includes a machine to machinegateway (M2M GW) 306. The machine to machine gateway 306 may include oneor more of the elements shown in FIG. 2 to allow machine to machinedevices to connect to the user equipment 302 b. In the implementationshown, machine to machine device 308 a and machine to machine device 308n (collectively or individually hereinafter identified as 308) arecoupled with the user equipment 302 b. As discussed above, this couplingmay be wired (e.g., Ethernet, power line, coaxial, fiber optic) orwireless (e.g., Zigbee, WLAN, Bluetooth). Machine to machine device 308a and machine to machine device 308 n include machine to machine clientapplication 310 a and machine to machine client application 310 n,respectively. Although not shown, a machine to machine device 308 mayinclude more than one machine to machine client application.

When the machine to machine device 308 connects with the user equipment302 b, the machine to machine device 308 may transmit registrationinformation to attach to the user equipment 302 b. The registrationinformation may include one or more of a device class and a deviceidentifier associated with the machine to machine device 308. Forexample, the device identifier may include a media access control (MAC)identifier, or a service provider unique identifier.

The user equipment 302 may be configured to couple with a radio accessnetwork (RAN) 310. The radio access network 310 may implement LTE,cdma2000, lx, or other radio access technology. As part of the coupling,the user equipment 302 may be configured to transmit a user equipmentidentifier to the RAN 310 which may be used to route traffic to the userequipment 302.

The user equipment 302 b may be further configured to assign a deviceconnection identifier to each machine to machine device 308 connectedwith the user equipment 302 b. In some implementations, the assignmentmay be performed at the machine to machine application level. Themachine to machine gateway 306 may use this assignment information tosend data to and receive data from the machine to machine device 308.For example, the machine to machine gateway 306 may ensure the packetsinclude the device connection information prior to transmission to theRAN 310. On the receiving end, when a packet is received from the RAN310, a portion of the packet (e.g., header field) may be interrogated toobtain the device connection identifier associated with the packet. Themachine to machine gateway 306 may then use this device identifier toroute the packet to the appropriate machine to machine device 308.

In some implementations, the RAN 310 is coupled with an IP anchor 314.The IP anchor 314 may include one or more of a packet gateway (P-GW), apacket data serving node (PDSN), a home agent (HA), or a locationmobility anchor (LMA). The IP anchor 314 may be configured to provide abridge between the radio domain and the packet data domain. As such, theIP anchor 314 may perform data communication with a machine to machine(M2M) server 316. The data communication received by machine to machineserver 316 may ultimately be serviced by a machine to machineapplication 318. In some implementations, the machine to machine server316 and the machine to machine server application 318 are controlled bya machine to machine service provider, such as a utility company orautomotive manufacturer as described above. In some implementations, theIP anchor 314 may be configured to communicate directly with the machineto machine server application 318.

In some implementations, such as that shown in FIG. 3, it may bedesirable for a service provider to also include a service provider (SP)authentication, authorization, and accounting (AAA) module 317. Thismodule may be implemented as a data storage configured to store usageinformation for the machine to machine server 316 and/or the machine tomachine server application 318. For example, as a data packet passesthrough the machine to machine server, the machine to machine server 316may identify the device connection information associated with thepacket. This may allow the machine to machine server 316 to identify themachine to machine device 308 that generated the packet. Based on one ormore of authentication, authorization, subscription, and the like, themachine to machine server 316 may process the packet. For example, ifthe machine to machine device 308 is subscribed for one transaction perweek and a second transaction is received, the machine to machine server316 may block the packet. In this case, the machine to machine server316 may be configured to transmit a response packet identifying thecause (e.g., subscription exceeded) and/or how to correct the issue(e.g., increasing the subscription level).

In some implementations, it may be desired to communicate with themachine to machine device 308 via a non-packet switched network. Forexample, the machine to machine server 316 may transmit information tothe machine to machine device using control plane signaling. In oneexample, the machine to machine server 316 may be configured tocommunicate with a machine to machine interworking framework (M2M-IWF)330. The machine to machine interworking framework 330 may receive acontrol plane signal from the machine to machine server 316. In oneimplementation, the machine to machine interworking framework 330 may becoupled with the IP anchor 314. In this implementation, the M2M-IWF 330may transmit the control signal to the IP anchor 314 for delivery asdescribed above. In some implementations, the M2M-IWF 330 may be furtherconfigured to translate the control plane signal into a packet signalfor transmission to the IP anchor 314.

In some implementations, the M2M server 316 or the M2M serverapplication 318 may transmit data to a machine to machine device 308 viaSMS messaging. The message may be received by an SMS service controller(SMS-SC)/IP short-message gateway (IP-SM-GW) 320. In thisimplementation, the SMS-SC/IP-SM-GW 320 may be configured to receive themessage and transmit the message to the IP anchor 314. In oneimplementation, the SMS-SC/IP-SM-GW 320 may communicate with the M2M-IWF330 to determine the PSDN associated with the intended messagerecipient. The SMS-SC/IP-SM-GW 320 may then establish a connection withthe identified IP anchor and transmit the SMS as an IP SMS packet. TheIP SMS packet may include one or more of the device identifier, deviceconnection identifier, and the user equipment identifier associated withthe machine to machine device 308 to receive the SMS message.

While the above communication paths have been described ascommunications originating with the machine to machine server 316 or themachine to machine server application 318 and destine for a machine tomachine device 308 or a machine to machine client application executedthereon, it will be understood that similar transmission patterns may beimplemented to allow the machine to machine device 308 to transmitcommunication to the machine to machine server 316 or the machine tomachine server application 318.

In some implementations, the M2M server 316 and/or the M2M serverapplication 318 may push a message to a M2M device 308. For example, ifa utility company is the service provider, during high electricitydemand periods, the utility company may transmit a demand responsesignal to smartmeters (M2M device 308) indicating a reduced usagesituation has arisen. The smartmeters may be configured, for example, toreduce the usage by disabling certain non-essential appliances. In thiscase, the location of the M2M device 308 may not necessarily be known.

When a UE 302 b first registers with the RAN 310, the RAN 310 maytransmit a record of the location of the UE 302 b to a mobilityswitching center (MSC)/visitor location record 324. In someimplementations, the RAN 310 may provide the user equipment identifierfor the UE 302 b. In some implementation, the RAN 310 may also providethe device connection identifier for the attached devices 308. In someimplementation, the RAN 310 may also provide the device identifier forthe attached devices 308. A corresponding record may be transmitted to ahome locator record (HLR)/authentication center (AC) 324. As part of theregistration, the RAN 310 may communicate with an authentication,authorization and accounting (AAA)/home subscriber server (HSS)/homelocation register (HLR) 312 (hereinafter referred to as “AAA 312”) toidentify whether the device may attach to the network, what servicelevel it may be provided, etc. In the context of packet data networks,when the UE 302 b registers with the RAN 310, an IP address may beassociated with the UE 302 b and/or the devices attached with the UE 302b.

After registration of the UE 302 b, the M2M server 316 may transmit amessage for a M2M device 308 n attached to the UE 302 b through one ormore communication pathways. In the packet data context, user planedevice triggering may be used to provide a message from a machine tomachine service provider to a machine to machine device. In thisimplementation, the M2M server 316 may transmit the triggering requestto the M2M-IWF 330. The triggering request may include an externalinterface identifier such as the device identifier and/or deviceconnection identifier. The M2M-IWF 330 may determine the IP address forthe device associated with the external interface identifier. Forexample, the M2M-IWF 330 may query one or both of the network operatorAAA 312 or service provider AAA 317 to identify the appropriate deviceconnection identifier to use for transmitting the triggering request. Aswith AAA 312, the service provider AAA 317 may be implemented as one ormore of an authentication, authorization and accounting (AAA) server, ahome subscriber server (HSS), and a home location register (HLR). In thecontext of packet data connections, the IP address may be used to createa data flow through the IP anchor 314 or the appropriate IP anchor forthe IP address. This in turn may cause the RAN 310 attached to the UE302 b to create a data flow for the device trigger. Once established,the data flow may be used for bi-directional packet data communicationbetween the device to be triggered and the M2M server 316.

Another communication pathway that may be used to trigger a device mayinclude 1× circuit short message delivery point-to-point (SMDPP)triggering. As above, the UE 302 b is registered with the networkoperator. In this case, the M2M-IWF 330 may query the network operatorAAA 312 to obtain an internal identifier for the network operator forthe device to be triggered. The internal identifier may be a compositeidentifier generated based on a mobile station identifier (MS_ID) or aninternational mobile subscriber identify (IMSI) for the UE 302 b and thedevice connection identifier for the M2M device 308 a. Once the internalidentifier is obtained, the M2M-IWF 330 may be configured to query thehome location record (HLR)/authentication center (AC) 324 to identifywhere the UE 302 b as well as the device 308 n is located. For example,the M2M-IWF 330 may send an SMSREQ message to the HLR/AC 325. Once thelocation is identified, a circuit call SMDPP may be initiated to themobility MSC/VLR 324 for the UE 302 b that the device 308 n is currentlyattached. For example, the M2M-IWF 330 may be configured to transmit aSMDPP signal which includes the device trigger and a communication. Bythis example, the M2M-IWF 330 may be configured to transmit the triggerrequest along with a new service indicator (SRVIND). The MSC/VLR 324 maytransmit an application data delivery service (ADDS) message to the RAN310 which the UE 302 b is attached. The ADDS message may include thedevice trigger such as a page message and a service option identifier.In some implementations, the service option identifier may be indicativethat the paging signal is a machine to machine device trigger page. TheADDS message, in turn, may cause a paging signal to be transmitted fromthe RAN 310 to the local access point 302 b. In some implementations,the paging signal may include the service option identifier. One or moreof the transmitted messages may be implemented using data burstmessaging. In some implementations, an existing data burst message typemay be used for machine to machine device triggering. In someimplementations, a new data burst message type may be defined for use inmachine to machine device triggering.

Yet another communication pathway that may be used to trigger a machineto machine device is cdma2000 1× special call identifier triggering. Insome implementations, it may be possible to trigger the device 308 nthrough the HRPD without IP/PPP. The UE 302 b first registers its userequipment identifier with the network operator such that the M2M-IWF 330may identify the location of the UE 302 b. The M2M-IWF 330 receives atrigger message from the M2M server 316. The M2M-IWF 330 may beconfigured to trigger a voice call with the UE 302 b. The RAN 310, inturn, may forward the trigger to the UE 302 b such as via paging. The UE302 b may transmit a paging response to the RAN 310. The RAN 310 maythen transmit an acknowledgment of the trigger to the M2M-IWF 330 thatmay, in turn, forward the acknowledgement to the M2M server 316. Once achannel is established between the UE 302 b and the network, the MSC/VLR324 may transmit a per-determined calling identifier to the UE 302 bindicating the trigger is a machine to machine trigger. The UE 302 b maybe configured to receive the calling identifier and end the call withoutanswering the call. In still another implementation, it may be possibleto deliver the M2M trigger using data burst message using the trafficchannel setup for voice call. In lieu of answering the call, the UE 302b may then establish data link with the IP anchor 314 through the RAN310 to the M2M server 316 either through HRPD or through IS2000 1×.Accordingly, the packet data link is established between the UE 302 b,and thus any locally attached M2M device 308, and the M2M server 316.This packet data link may be used to communicate directly with the M2Mdevice 308 as described above.

Still another communication pathway that may be used to trigger amachine to machine device is cdma2000 1× circuit call with a machine tomachine service option. This communication pathway is substantiallysimilar to the cdma2000 1× special call identifier triggering describedabove. However, instead of avoiding the answering of the call, in thispathway, the call is setup between the UE 302 b and the network (e.g.,the MSC/VLR 324 via the RAN 310). Once the call is established, the datamay be transmitted via the circuit call from the M2M-IWF 330 to the UE302 b. The UE 302 b may then be configured to pass the trigger to thedevice 308 to be triggered. In some implementations, the M2M-IWF 330 mayhost a circuit switched application. The hosted circuit switchedapplication hosted by the M2M-IWF 330 may act as a peer to acorresponding circuit switched application configured at the UE 302 b.As such, the M2M-IWF 330 and the UE 302 b (and thus the M2M device 308connected thereto) may communication using circuit switch callsignaling. In some implementations the communication may be performedover a dedicated channel.

One or more of the RAN 310, the IP anchor 314, and the M2M-IWF 330 maybe configured to communicate with an AAA/RAN AAA 312. In someimplementations the AAA/RAN AAA 312 may be provided by the networkoperator. The AAA/RAN AAA 312 may include authentication, authorization,and accounting information. This information may be used to controlcommunications on the operator's network. In some implementations, theinformation may be stored in a data storage coupled with the AAA/RAN AAA312. The information may be associated with a one or more of a deviceclass, a device connection identifier, a device identifier, a userequipment identifier, or any combination of these. The information mayidentify types of packets that are allowed for an identified device ordevice class. The information may also be used to generate accountinginformation (e.g., billing information based on network resource usagequantity, type, and/or time) for a device, local host/user equipment, orservice provider.

Although a number of separate components are illustrated in FIG. 3,those of skill in the art will recognize that one or more of thecomponents may be combined or commonly implemented. Further, each of thecomponents illustrated in FIG. 3 may be implemented using a plurality ofseparate elements.

FIG. 4 shows a call flow diagram for an exemplary device binding. Thecall flow begins with the M2M device 308 a provides a service layerregistration 402. The service layer registration may include informationabout the M2M device 308 a such as the device identifier, the deviceURL, external interface identifier, the device class, and user equipmentidentifier. As shown in FIG. 4, service layer registration 402 mayinclude information about multiple M2M devices. Each service layerregistration 402 may correspond to a device and/or an applicationconfigured to execute on an M2M device 308.

The service layer registration 402 may be predefined for each servicelayer. For example the registration information may be stored in memory.In some implementations, the registration information may be receivedusing over the air provisioning, or via a data connection with theservice provider. The M2M server 316 maintains a record of the M2Mdevice 308 registration. For example, the M2M server 316 may be coupledwith a service provider AAA/database to store the registrationinformation 404. In some implementations, this information may be storedwhen the M2M device 308 is manufactured. In some implementations, thisinformation may be stored when the M2M device 308 is activated.

The M2M device 308 a and the M2M device 308 n may then connect to thelocal access point 302 b via call 406. The connection may be, forexample, through a local area network (LAN). The local access point 302b may be configured to assign a device connection identifier to each ofthe M2M device 308 a and the M2M device 308 n as described above. Insome implementations, the local access point may be configured to usenetwork address translation (NAT). In these implementations, the deviceconnection identifier may be an external port identifier that is used bythe device 308 along with the external IP address (e.g., IP address ofthe local access point 302 b) assigned by the IP anchor 314. As trafficpasses through the local access point 302 b, the local access point 302b may be configured to modify the IP information included in the traffic(e.g., IP packet header), to identify the device 308 associated with thetraffic. In this way, packets flowing from the device 308 through thelocal access point 302 b will be identifiable as from the device 308.Similarly, a packet transmitted for the device 308 may use the IPinformation to identify not only the local access point 302 b, but alsothe device 308 which should receive the packet. In some implementations,the local access point 302 b may be configured to use IPv6 addressing.In these implementations, the device connection identifier may be theIPv6 interface identifier that is used along with the IPv6 prefix thatis assigned by IP anchor 314. Although described in the alternative, alocal access point 302 may be configurable to perform both NAT and IPv6addressing.

In some implementations IP anchor 314 may use the IP header to controlthe device 308. Based on the IP header alone, the IP anchor 314 may nothave visibility into the application header for traffic originating fromthe device 308. The IP address for all the devices 308, as seen by theIP anchor 314, is the same external IP address that is assigned to thelocal access point 302 b. However, the private IP address of each device308 may be different behind the NAT module of the local access point 302b. Accordingly, in some implementations, it may be desirable to enablethe IP anchor 314 to control each of the devices 308 behind the NATmodule of the local access point 302 b.

Once assigned, the local access point 302 b may be configured totransmit the assignment information for the connected devices to thenetwork through call 408. For example, the local access point maytransmit to the IP anchor 314 the external port identifier that isassigned by the NAT module configured in the local access point to eachof the connected devices. In another implementation, the local accesspoint may transmit to the IP anchor 314 the interface identifier that isassigned by the IPv6 module configured in the local access point to eachof the connected devices. As shown in FIG. 4, one call transmits theassignment information for M2M device 308 a and M2M device 308 n. Insome implementations, separate calls may be made for eachdevice/application assignment. The assignment information may betransmitted through the RAN to the IP anchor 314. Various protocols maybe used to transmit the assignment information such as RSVP, packet datanetwork attach procedures, access network discovery and selectionfunctions, and control plane signaling. If RSVP is used, one or morefields may be added to the 5-tuple that is sent in the RSVP to includethe assignment information. For example, a RSVP 5-tuple may include:source IP address, destination IP address, source port number,destination port number, and protocol number. An additional field may beincluded to include the device connection identifier. The additionalfield may also include the device identifier. Alternatively, yet anotherseparate field may be included to specify the device identifier. In someimplementations, the assignment information may also be transmittedthrough the RAN to the mobility switching center. The assignmentinformation may also be transmitted to the network operator AAA 312.

The assignment information transmitted may be a suggested assignment.The network operator may further process the assignment suggested by thelocal access point 302 b. If the network operator determines theassignment is appropriate the network may transmit a confirmation of theassignment to the local access point 402 b at call 410. If the networkdetermines the assignment is inappropriate, the network may transmit analternate assignment to the local access point 402 b at call 410. Thedetermination of the appropriateness of a suggested assignment may bebased on one or more of the device identifier, the device class, thelocal access point, the service provider for the device, networkconditions, and the like.

In some implementations, the local access point 302 b may not transmitthe assignment information. In some implementations it may be desirableto allow the network operator to assign the connection identifier forthe connected devices. In this implementation, the local access point302 b may transmit the device identifier to the network (e.g., IP anchor314). The network operator may then transmit the assignment informationto the local access point 302 b via call 410. For example, theassignment information may be transmitted via RSVP. In someimplementations, control plane signaling may be used to transmit theassignment information. Once agreed upon, the assignment information maybe forwarded from the IP anchor 314 to the network operator AAA 312 atcall 412. The network operator AAA 312 may be configured to store theassignment information (e.g., device identifier, device connectionidentifier, user equipment identifier) at call 414. For example, thenetwork operator AAA 312 may include a data storage configured tomaintain a mapping between the connection information and the devicesencompassing the connection.

In some implementations, the assignment information may be used the AAA312 of the network operator as well as the service provider AAA 317 todetermine control for the identified M2M device. For example, thenetwork operator AAA 312 may only include subscription information forthe local access point 302. In this example, the service provider AAA317 will communicate with the service provider AAA 317 to refine thecontrol for the M2M device 308 a. In some implementations, the networkoperator AAA 312 may include both the information associated with thelocal access point 302 and the M2M device 308 a. In someimplementations, the network operator AAA 312 may derive the controlinformation for the M2M device 308 a based at least in part on theassignment information. For example, the network operator AAA 312 maytransmit a query generated based on information from the assignmentinformation to the service provider AAA 317. In this example, theservice provider AAA 317 may respond with appropriate controlinformation for the identified M2M device. In some implementations, thecontrol information may be based at least in part on an agreementbetween the network operator and the service provider.

Once the control information has been obtained, at call 416 thepreconfigured communication link or online communication link may bebuilt for the local access point 302 b. At 418, a policy is determinedfor the local access point and/or M2M device. The policy may bedetermined based at least in part on the network load, local accesspoint information, M2M device information, service provider, etc. Insome implementations, the policy may be provided to the IP anchor 314via the M2M-IWF 330. In these implementations, the policy may betransmitted to the M2M-IWF 330 at call 420. The policy may betransmitted as a push message from the network operator AAA 312 to theM2M-IWF 330. In some implementations, the M2M-IWF 330 may be configuredto pull the policy information from the network operator AAA 312 such asvia a query. At call 420, the policy may be transmitted from the M2M-IWF330 to the IP anchor 314. At call 422, the policy information may besent to the M2M server 316 from the M2M-IFW 330. The network operatorAAA 312 may include one or more of the URL, device identifier, or deviceconnection identifier in the policy information. The policy informationmay be transmitted based on the M2M device 308 involved in thecommunication. When transmitting the policy information from the M2M-IWF330 to the IP anchor 314 (e.g., call 422), the policy information mayinclude one or more of the device identifier and the device connectioninformation.

A similar push or pull mechanism as described above may be used toprovide the policy to the IP anchor 314. In some implementations, it maybe desirable to configure the IP anchor 314 to directly receive thepolicy information from the network operator AAA 312. For example, atcall 424, the IP anchor 314 may be configured to pull the policyinformation from the network operator AAA 312. The network operator AAA312 may be configured to push the policy information to the IP anchor314.

At call 426, the policy information may be provided to the local accesspoint 302 b and M2M device 308 via push or pull as described above. Insome implementations, the policy information provided to the localaccess point 302 b includes the device identifier and the deviceconnection identifier for the device involved in the communication path.In some implementations, the policy information transmitted at call 426may be transmitted through RSVP or packet data signaling.

Once the M2M device 308 a has been bound, forward link control may beexercised for the M2M device 308 a. For example, the M2M IWF 330 may beconfigured to provide the policy to the M2M-server on a per M2M deviceidentified using M2M connection identifier to block or delay certaindevice classes. The M2M-IWF 330 may be configured to query the AAA 312or SP AAA 317 for device identity and device connection info to block ordelay certain devices or device classes that connected to the localaccess point 302 b. The device connection info and associated policy maybe sent to IP anchor 314 (e.g., the IP anchor) or the MSC/SMS center(e.g., the data anchor). Accordingly, the IP anchor or data anchor maybe configured to enforce the policy for the corresponding connection forthe M2M device 308 a. The IP anchor will use the external deviceidentifier embedded in the address of the packets targeted for M2Mdevice to enforce the policy. For example, the port number used by theNAT module configured at the local access point, that is embedded in theIP header to control the M2M device.

Once the M2M device 308 a has been bound, reverse link control may alsobe exercised for traffic of the M2M device 308 a. The network operatormay provide the policy to the local access point 302 b to block or delaycertain devices or device classes that connected to the local accesspoint 302 b. The RAN may be configured to send this policy informationthrough overhead messages. The network may be configured to transmit thepolicy information through an access network discovery and selectionfunction (ANDSF), PPP, or RSVP. The local access point 302 b may thenenforce the policy for the corresponding device connection identifier.Packets may be dropped by the network (e.g., IP anchor) based on thedevice connection identifier of the device (IID/Port number) generatingthe traffic. As described above, the device connection identifier may beincluded in the transmitted traffic (e.g., in a header field).

FIG. 5 shows a process flow diagram of an exemplary process for bindinga plurality of devices to a user equipment. The method may be performedby one or more of the devices described herein, such as, for example,the device 202 shown in FIG. 2 or the device shown below in FIG. 6. Insome implementations, the process may be implemented in/by a localaccess point 106 d.

The process shown in FIG. 5 may generally be described as an assignmentprocess. The user equipment may be configured to assign connectioninformation for each device connected to (e.g., locally hosted by) theuser equipment. The local hosting may be via a first network such as alocal area network (e.g., Bluetooth, Zigbee, WiFi, Z-wave, etc.). Theassigned information may then be transmitted to the network operator viaa second network (e.g., wide area or local area network) providingservice to the user equipment. When a network entity receives acommunication for the device, the assigned information may be used toidentify not just the user equipment, but also the device to receive thecommunication.

At block 502, a message is received via a first network from at leastone of the plurality of devices. The message includes informationidentifying each device connected with the user equipment. In someimplementations, receiving the method includes receiving the message viaa local network connection. The message may include a device class foreach device. A device class generally provides information about theassociated device such as data rate, intended usage pattern (e.g., data,voice, hybrid), capability for the device (e.g., radio accesstechnology), and the like. As discussed above, the informationidentifying each device may include a media access control (MAC)identifier, an international mobility equipment identity, or aninternational mobility subscriber identity.

At block 504, a device connection identifier is assigned to the device.The device connection identifier includes at least a portion of the userequipment identifier associated with the user equipment. In someimplementations, assigning the device connection identifier includesassigning an interface identity identifier to the device. The assignmentof the device connection identifier may include assigning a port numberto the device connection identifier. The assignment may include storingthe connection identifier in a memory along with the associatedinformation identifying the device.

At block 506, information indicative of the assignment of the deviceconnection identifier are transmitted to a network operator via a secondnetwork. In some implementations, information indicative of theidentified device may also be transmitted. This information may be usedto allow data communication to the device from the network operatorbased at least in part on the device connection identifier. In someimplementations, the network operator may provide this information to aM2M service provider, such as a utility company or electronic-mediaprovider. An example data communication is a packet data communicationwhere the packet data communication includes the device connectionidentifier for the device. In some implementations, the packet datacommunication may include a control signal (e.g., trigger) for thedevice. In some implementations, the transmission of block 506 mayfollow one or more of RSVP, PPP, or other packet data network attachprocedures.

FIG. 6 shows a functional block diagram of another exemplary device thatmay be employed within the communication system of FIG. 1. The device600 may be implemented as a local host/user equipment configured tolocally host a plurality of communication devices. A local hostingdevice may have more components than the simplified device 600 shown inFIG. 6. The communication device 600 shown includes only thosecomponents useful for describing some prominent features of certainimplementations. The device 600 includes a receiving circuit 602, anassigning circuit 604, and a transmitting circuit 606.

In some implementations the receiving circuit 602 is configured toreceive a message from at least one of a plurality of communicationdevices via a first network (e.g., local area network), the messageincluding information identifying the communication device connectedwith the device 600. The receiving circuit 602 may include one or moreof an antenna, a receiver, and a processor. In some implementations,means for receiving include the receiving circuit 602.

The assigning circuit 604 may be configured to assign a deviceconnection identifier to the communication device, the device connectionidentifier including at least a portion of a user equipment identifierassociated with the device 600. The assigning circuit 604 may includeone or more of a processor, a network interface, and a memory. In someimplementations, means for assigning may include the assigning circuit704.

The transmitting circuit 606 may be configured to transmit, via a secondnetwork (e.g., local area network and/or wide area network) informationindicative of the assignment of the device connection identifier to anetwork operator, such that data communication to the communicationdevice from the network operator is based at least in part on the deviceconnection identifier. The transmitting circuit 606 may include one ormore of a processor, an antenna, a transmitter, and a memory. In someimplementations, means for transmitting include the transmitting circuit606.

FIG. 7 shows a process flow diagram of another exemplary process forbinding a plurality of devices to a user equipment. The method may beperformed by one or more of the devices described herein, such as, forexample, the device 202 shown in FIG. 2 or the device shown below inFIG. 8. In some implementations, the process may be implemented in/by alocal access point 106 d.

The process shown in FIG. 7 may generally be described as a look-upprocess. The user equipment transmits information associated with anattached device to a network operator via a first network such as alocal area network or wide area network. The network operator (or aservice provider coupled therewith) then provides the connectioninformation for the identified device to the user equipment.

At block 702 registration information including an identifier for atleast one of the plurality of devices connected with the user equipmentis transmitted from the user equipment to a network operator via a firstnetwork. Each device is connected to the user equipment via a secondnetwork. In some implementations, the first network includes a local orwide area network such as a cellular network. The registrationinformation may be received from the device via the second network suchas a local area network (e.g., Bluetooth, Zigbee, WiFi, Z-wave, etc.).The transmission may be a wired or wireless transmission. It may bedesirable, in some implementations, to transmit a device class for theconnected device. The identifier for each device may include one or moreof a media access control identifier, an international mobility entityidentifier, or an international mobility subscriber identity.

At block 704, a device connection identifier for each device is receivedfrom the network operator. The device connection identifier includes atleast a portion of a user equipment identifier associated with the userequipment. The device connection identifier may indicate a connectionbetween each device and the user equipment on the second network. Theuser equipment identifier may include one or more of a media accesscontrol identifier, an international mobility entity identifier, or aninternational mobility subscriber identity. The device connectionidentifier may include an interface identity identifier and a port forthe connection. In some implementations, the device connectionidentifier and/or device class may be used to determine a quality ofservice for the device.

At block 706, a data communication is received from the network operatorbased at least in part on the device connection identifier. Inimplementations where the quality of service is also based on the deviceconnection identifier, the data communication is further subjected tothe associated quality of service. The data communication may include apacket data network communication.

FIG. 8 shows a functional block diagram of another exemplary device thatmay be employed within the communication system of FIG. 1. The device800 may be implemented as a user equipment configured to locally host aplurality of communication devices. A user equipment device may havemore components than the simplified device 800 shown in FIG. 8. Thedevice 800 shown includes only those components useful for describingsome prominent features of certain implementations. The device 800includes a transmitting circuit 802, a receiving circuit 804, and a datacommunication circuit 806.

The transmitting circuit 802 may be configured to transmit from thedevice 800 to a network operator via a first network registrationinformation including an identifier for at least one of the plurality ofcommunication devices. The transmitting circuit 802 may include one ormore of a processor, an antenna, a transmitter, and a memory. In someimplementations, means for transmitting include the transmitting circuit802.

The receiving circuit 804 may be configured to receive a deviceconnection identifier for the communication device from the networkoperator, the device connection identifier including at least a portionof a user equipment identifier associated with the local host/userequipment device 800. The device connection identifier indicates aconnection between the communication device and the local host/userequipment device 800 on the second network. The receiving circuit 804may include one or more of an antenna, a receiver, and a processor. Insome implementations, means for receiving include the receiving circuit804.

The data communication circuit 806 may be configured to receive, via thefirst network, data communication from the network operator based atleast in part on the device connection identifier. The datacommunication circuit 806 may include one or more of a signal processor,a receiver, an antenna, and a memory. In some implementations, means fordata communication may include the data communication circuit 806.

FIG. 9 shows a process flow diagram of an exemplary process of binding adevice to a user equipment. The process shown in FIG. 9 may beimplemented in, for example, the device 202 shown in FIG. 2 or asdescribed below in FIG. 10. In some implementations, the process may beimplemented in/by a machine to machine device 112 a coupled with a localaccess point 106 d. The process of binding for a device to a userequipment shown in FIG. 9 is applicable whether the binding is performedaccording to an assignment or a look-up as described above in FIGS. 5and 7, respectively.

At block 902, a message is transmitted, via a first network such as alocal area network, from the device to the user equipment. The messageincludes information identifying the device connected to the userequipment. The transmission may be wired or wireless transmission. Insome implementations, the transmission may be via a local networkconnection. The message may include a device class for the identifieddevice.

At block 904, a device connection identifier is received from the userequipment at the device via the first network. The device connectionidentifier includes at least a portion of the user equipment identifierassociated with the user equipment. In some implementations, quality ofservice information for the device and/or device class may be received.

At block 906, a data communication is received from the user equipmentvia the first network based at least in part on the device connectionidentifier. The data communication is received by the user equipment viaa second network. For example, the data communication may originate froma machine to machine service provider as discussed above. The datacommunication is received through a provider network (e.g., local and/orwide area network) at the user equipment. The user equipment thentransmits the data communication to the device. The first and secondnetworks may comprise different communication protocols, methods, radioaccess technologies, quality of service, etc. In some implementations,the data communication comprises a packet data communication.

FIG. 10 shows a functional block diagram of another exemplary devicethat may be employed within the communication system of FIG. 1. Thedevice 1000 may be implemented as a device (e.g., machine to machinedevice 112) for binding with a user equipment. A locally hosted devicemay have more components than the simplified device 1000 shown in FIG.10. The device 1000 shown includes only those components useful fordescribing some prominent features of certain implementations. Thedevice 1000 includes a transmitting circuit 1002, a receiving circuit1004, and a data communication circuit 1006.

The transmitting circuit 1002 may be configured to transmit a messagefrom the device 1000 to the user equipment, the message includinginformation identifying the device 1000 connected with the userequipment via a first network (e.g., local area network). Thetransmitting circuit 1002 may include one or more of a processor, anantenna, a transmitter, and a memory. In some implementations, means fortransmitting include the transmitting circuit 1002.

The receiving circuit 1004 may be configured to receive a deviceconnection identifier from the user equipment at the device 1000, thedevice connection identifier including at least a portion of a userequipment identifier associated with the user equipment. The receivingcircuit 1004 may include one or more of an antenna, a receiver, and aprocessor. In some implementations, means for receiving include thereceiving circuit 804.

The data communication circuit 1006 may be configured to receive, viathe first network, a data communication from the user equipment based atleast in part on the device connection identifier. The datacommunication may be received by the user equipment via a second networkas described above. The data communication circuit 1006 may include oneor more of a signal processor, a receiver, an antenna, and a memory. Insome implementations, means for data communication may include the datacommunication circuit 1006.

FIG. 11 shows a process flow diagram of an exemplary process fortriggering a device hosted by a local host/user equipment. The processshown in FIG. 11 may be implemented, for example, using the device asdescribed above in FIG. 2 or below in FIG. 12. In some implementations,this method may be included in an access point 104 (e.g., an IWF) asdescribed above. At block 1102, a device triggering request is receivedat an operator network. The device triggering request may include adevice identifier associated with the device to be triggered. The deviceto be triggered may be connected to the user equipment via a firstnetwork such as a local area network.

At block 1104, a user equipment hosting the device is identified basedat least in part on the device identifier. In some implementations, theidentification may include querying a home locator record for the localhost/user equipment, the query based at least in part on the identifierassociated with the device to be triggered.

At block 1106, a communication link in a second network to the localhost/user equipment is initiated, the communication link based at leastin part on information identifying the device to be triggered. Thecommunication link may include a circuit call such as a cdma2000 1×circuit call. In some implementations, the initiation of thecommunication link is further based on a service option identifier. Aservice option identifier may generally refer to a value correspondingto a communication link characteristic such as forward or reverse linkmultiplexing, as forward or reverse link data rates, and the like.

At block 1108, the device triggering request is transmitted to the localhost/user equipment via the second network. In some implementations, thetransmission of the triggering request to the local host/user equipmentmay include receiving a request for a second communication link from thelocal host/user equipment and transmitting the device triggering requestto the local host/user equipment via the second communication link. Thesecond communication link may not necessarily be the same (e.g.,network, radio access technology) as the communication link initiated atblock 1106. In some implementations, the second communication link mayinclude a data packet communication link. It may be desirable to receivean acknowledgment that the device was triggered, such as via a pagingresponse.

FIG. 12 shows a functional block diagram of another exemplary devicethat may be employed within the communication system of FIG. 1. Acommunication device may have more components than the simplifiedwireless communication device 1200 shown in FIG. 12. The communicationdevice 1200 shown includes only those components useful for describingsome prominent features of certain implementations. The communicationdevice 1200 includes a receiving circuit 1202, an identifying circuit1204, a call initiating circuit 1206, and a transmitting circuit 1208.

The receiving circuit 1202 may be configured to receive, at an operatornetwork, a device triggering request including a device identifierassociated with the device to be triggered. The device to be triggeredmay be connected to the user equipment via a first network. Thereceiving circuit 1202 may include one or more of a memory, a processor,and a signal detector. In some implementations means for receivinginclude a receiving circuit 1202.

The identifying circuit 1204 may be configured to identify the locationof a local host/user equipment for the device based at least in part onthe device identifier. The identifying circuit 1204 may include one ormore of a memory, a processor, and a location circuit. In someimplementations, means for identifying include the identifying circuit1204.

The call initiation circuit 1206 may be configured to initiate acommunication link to the local host/user equipment in a second network,the communication link based at least in part on information identifyingthe device to be triggered. The call initiation circuit 1206 may includea signal detector, a memory, and a transmitter. In some implementations,means for initiating include the call initiation circuit 1206.

The transmitting circuit 1208 may be configured to transmit the devicetriggering request to the local host/user equipment via the secondnetwork. The transmitting circuit 1208 may include one or more of aprocessor, an antenna, a transmitter, and a memory. In someimplementations, means for transmitting include the transmitting circuit1208.

FIG. 13 shows a process flow diagram of a method of communication to adevice hosted by a user equipment. The method shown in FIG. 13 may beimplemented in/by one or more of the devices described herein, such asthe device 202 shown in FIG. 2 or below in FIG. 14. In someimplementations, the process may be implemented in/by a local accesspoint 106 d.

At block 1302, information relating a network identifier for the deviceto a service identifier for the device is stored at the user equipment.In some implementations, the network identifier may include a permanentnetwork access identifier. The service identifier may be associated witha subscription to a service for the device.

At block 1304, routing information and the network identifier isreceived from a network operator via a first network. The first networkmay include a wide area network and/or a local area network. The routinginformation may include a temporary international mobile subscriberidentity assigned by a local radio access network and one or more of asubnet identifier and a packet data serving node identifier. The userequipment may now have the information needed to transmit information tothe device. Similarly, the local radio access network may have theinformation needed to route information not just to the local host/userequipment but to a specific device coupled with the local host.

At block 1306, a message including the service identifier is receivedvia the first network. The message may be targeted for the device. Themessage may be received by the local host/user equipment from thenetwork operator. The message may be generated by a service providerassociated with the network operator such as a utility service provider.

At block 1308, the routing information and the network identifier areobtained based at least in part on the service identifier. For example,the information received at block 1302 and block 1304 may be stored in amemory such as a look up table. Using the service identifier in thereceived message, the routing information and network identifier may bedetermined.

At block 1310, at least a portion of the received message istransmitted, via a second network (e.g., local area network) to thedevice based, at least in part, on the obtained routing information. Insome implementations, the message may be transformed or otherwisereformatted for transmission to the device.

FIG. 14 shows a functional block diagram of another exemplary devicethat may be employed within the communication system of FIG. 1. A devicemay have more components than the simplified device 1400 shown in FIG.14. The device 1400 shown includes only those components useful fordescribing some prominent features of certain implementations. Thedevice 1400 may be configured for communicating with a communicationsdevice connected to the device 1400. In some implementations, the device1400 may be implemented in/as a local host or gateway. The device 1400includes a memory 1402, a routing receiver 1404, a message receiver1406, a message routing processor 1408, and a transmitting circuit 1410.

The memory 1402 is configured to store information relating a networkidentifier for the communications device to a service identifier for thecommunications device. The memory 1402 may include one or more of astatic memory, a volatile memory, a non-volatile memory, a networkedmemory, a native memory, or other suitable storage medium. In someimplementations, means for storing information may include the memory1402.

The routing receiver 1404 is configured to receive, from a networkoperator via a first network, routing information and the networkidentifier. The routing receiver 1404 may include one or more of anantenna, a receiver, a signal processor, a processor, and a memory. Insome implementations, means for receiving routing information and thenetwork identifier may include the routing receiver 1404.

The message receiver 1406 is configured to receive a message, via thefirst network, including the service identifier, the message targetedfor the communication device. The message receiver 1406 may include oneor more of an antenna, a receiver, a signal processor, a processor, anda memory. In some implementations, the message receiver 1406 and therouting receiver 1404 may be commonly implemented in whole or in part.Means for receiving a message may include the message receiver 1406.

The message routing processor 1408 is configured to obtain the routinginformation and the network identifier based at least in part on theservice identifier. The message routing processor 1408 may include oneor more of a memory, a processor, a comparator, and a look up table.Means for obtaining the routing information and the network identifiermay include the message routing processor.

The transmitting circuit 1410 is configured to transmit at least aportion of the message to the communications device via a secondnetwork, the transmitting based at least in part on the obtained routinginformation. The transmitting circuit 1410 may include one or more of anantenna, a signal generator, a transmitter, and a power source. Meansfor transmitting at least a portion of the message to the communicationdevice may include the transmitting circuit 1410.

As used herein, the term “determining” encompasses a wide variety ofactions. For example, “determining” may include calculating, computing,processing, deriving, investigating, looking up (e.g., looking up in atable, a database or another data structure), ascertaining and the like.Also, “determining” may include receiving (e.g., receiving information),accessing (e.g., accessing data in a memory) and the like. Also,“determining” may include resolving, selecting, choosing, establishingand the like. Further, a “channel width” as used herein may encompass ormay also be referred to as a bandwidth in certain aspects.

As used herein, a phrase referring to “at least one of” a list of itemsrefers to any combination of those items, including single members. Asan example, “at least one of: a, b, or c” is intended to cover: a, b, c,a-b, a-c, b-c, and a-b-c.

The various operations of methods described above may be performed byany suitable means capable of performing the operations, such as varioushardware and/or software component(s), circuits, and/or module(s).Generally, any operations illustrated in the Figures may be performed bycorresponding functional means capable of performing the operations.

The various illustrative logical blocks, modules and circuits describedin connection with the present disclosure may be implemented orperformed with a general purpose processor, a digital signal processor(DSP), an application specific integrated circuit (ASIC), a fieldprogrammable gate array signal (FPGA) or other programmable logic device(PLD), discrete gate or transistor logic, discrete hardware componentsor any combination thereof designed to perform the functions describedherein. A general purpose processor may be a microprocessor, but in thealternative, the processor may be any commercially available processor,controller, microcontroller or state machine. A processor may also beimplemented as a combination of computing devices, e.g., a combinationof a DSP and a microprocessor, a plurality of microprocessors, one ormore microprocessors in conjunction with a DSP core, or any other suchconfiguration.

In one or more aspects, the functions described may be implemented inhardware, software, firmware, or any combination thereof. If implementedin software, the functions may be stored on or transmitted over as oneor more instructions or code on a computer-readable medium.Computer-readable media includes both computer storage media andcommunication media including any medium that facilitates transfer of acomputer program from one place to another. A storage media may be anyavailable media that can be accessed by a computer. By way of example,and not limitation, such computer-readable media can comprise RAM, ROM,EEPROM, CD-ROM or other optical disk storage, magnetic disk storage orother magnetic storage devices, or any other medium that can be used tocarry or store desired program code in the form of instructions or datastructures and that can be accessed by a computer. Also, any connectionis properly termed a computer-readable medium. For example, if thesoftware is transmitted from a website, server, or other remote sourceusing a coaxial cable, fiber optic cable, twisted pair, digitalsubscriber line (DSL), or wireless technologies such as infrared, radio,and microwave, then the coaxial cable, fiber optic cable, twisted pair,DSL, or wireless technologies such as infrared, radio, and microwave areincluded in the definition of medium. Disk and disc, as used herein,includes compact disc (CD), laser disc, optical disc, digital versatiledisc (DVD), floppy disk and Blu-ray disc where disks usually reproducedata magnetically, while discs reproduce data optically with lasers.Thus, in some aspects computer readable medium may comprisenon-transitory computer readable medium (e.g., tangible media). Inaddition, in some aspects computer readable medium may comprisetransitory computer readable medium (e.g., a signal). Combinations ofthe above should also be included within the scope of computer-readablemedia.

The methods disclosed herein comprise one or more steps or actions forachieving the described method. The method steps and/or actions may beinterchanged with one another without departing from the scope of theclaims. In other words, unless a specific order of steps or actions isspecified, the order and/or use of specific steps and/or actions may bemodified without departing from the scope of the claims.

The functions described may be implemented in hardware, software,firmware or any combination thereof. If implemented in software, thefunctions may be stored as one or more instructions on acomputer-readable medium. A storage media may be any available mediathat can be accessed by a computer. By way of example, and notlimitation, such computer-readable media can comprise RAM, ROM, EEPROM,CD-ROM or other optical disk storage, magnetic disk storage or othermagnetic storage devices, or any other medium that can be used to carryor store desired program code in the form of instructions or datastructures and that can be accessed by a computer. Disk and disc, asused herein, include compact disc (CD), laser disc, optical disc,digital versatile disc (DVD), floppy disk, and Blu-ray® disc where disksusually reproduce data magnetically, while discs reproduce dataoptically with lasers.

Thus, certain aspects may comprise a computer program product forperforming the operations presented herein. For example, such a computerprogram product may comprise a computer readable medium havinginstructions stored (and/or encoded) thereon, the instructions beingexecutable by one or more processors to perform the operations describedherein. For certain aspects, the computer program product may includepackaging material.

Software or instructions may also be transmitted over a transmissionmedium. For example, if the software is transmitted from a website,server, or other remote source using a coaxial cable, fiber optic cable,twisted pair, digital subscriber line (DSL), or wireless technologiessuch as infrared, radio, and microwave, then the coaxial cable, fiberoptic cable, twisted pair, DSL, or wireless technologies such asinfrared, radio, and microwave are included in the definition oftransmission medium.

Further, modules and/or other appropriate means for performing themethods and techniques described herein can be downloaded and/orotherwise obtained by a user terminal and/or base station as applicable.For example, such a device can be coupled to a server to facilitate thetransfer of means for performing the methods described herein.Alternatively, various methods described herein can be provided viastorage means (e.g., RAM, ROM, a physical storage medium such as acompact disc (CD) or floppy disk, etc.), such that a user terminaland/or base station can obtain the various methods upon coupling orproviding the storage means to the device. Moreover, any other suitabletechnique for providing the methods and techniques described herein to adevice can be utilized.

It is to be understood that the claims are not limited to the preciseconfiguration and components illustrated above. Various modifications,changes and variations may be made in the arrangement, operation anddetails of the methods and apparatus described above without departingfrom the scope of the claims.

While the foregoing is directed to aspects of the present disclosure,other and further aspects of the disclosure may be devised withoutdeparting from the basic scope thereof, and the scope thereof isdetermined by the claims that follow.

What is claimed is:
 1. A method of communication to a device hosted by auser equipment, the method comprising: storing, at the user equipment,information based on a network identifier for the device and a serviceidentifier for the device; receiving, at the user equipment from anetwork operator via a first network, routing information and thenetwork identifier; receiving, at the user equipment from the networkoperator via the first network, a message including the serviceidentifier; obtaining the routing information and the network identifierbased on the service identifier; and transmitting, via a second network,the message to the device, the transmitting based on the obtainedrouting information.
 2. The method of claim 1, wherein the first networkcomprises at least one of a wide area network and a local area network.3. The method of claim 1, wherein the second network comprises a localarea network.
 4. The method of claim 1, wherein the network identifiercomprises a permanent network access identifier.
 5. The method of claim1, further comprising mapping the received network identifier to theservice identifier.
 6. The method of claim 1, wherein the routinginformation comprises a temporary international mobile subscriberidentity assigned by a local radio access network and one or more of asubnet identifier and a packet data serving node identifier.
 7. Themethod of claim 1, wherein receiving the message comprises receiving acommunication from a machine-to-machine server for the device.
 8. Themethod of claim 1, wherein the service identifier comprises asubscription identifier.
 9. An apparatus for communicating with a devicelocally hosted by the apparatus, the apparatus comprising: a memorystoring information based on a network identifier for the device and aservice identifier for the device; a receiver configured to receive,from a network operator via a first network, routing information and thenetwork identifier, the receiver further configured to receive amessage, via the first network, including the service identifier; aprocessor configured to obtain the routing information and the networkidentifier based on the service identifier; and a transmitter configuredto transmit, via a second network, the message to the device, thetransmitting based on the obtained routing information.
 10. Theapparatus of claim 9, wherein the first network comprises at least oneof a wide area network and a local area network.
 11. The apparatus ofclaim 9, wherein the second network comprises a local area network. 12.The apparatus of claim 9, wherein the network identifier comprises apermanent network access identifier.